|
High-level design (HLD) explains the architecture that would be used for developing a software product. The architecture diagram provides an overview of an entire system, identifying the main components that would be developed for the product and their interfaces. The HLD uses possibly nontechnical to mildly technical terms that should be understandable to the administrators of the system. In contrast, low-level design further exposes the logical detailed design of each of these elements for programmers. == Purpose == * Preliminary design—In the preliminary stages of a software development, the need is to size the project and to identify those parts of the project that might be risky or time consuming. * Design overview—As the project proceeds, the need is to provide an overview of how the various sub-systems and components of the system fit together. In both cases the high-level design should be a complete view of the entire system, breaking it down into smaller parts that are more easily understood. To minimize the maintenance overhead as construction proceeds and the lower-level design is done, it is best that the high-level design is elaborated only to the degree needed to satisfy these needs. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「High-level design」の詳細全文を読む スポンサード リンク
|